Merged
Conversation
Contributor
|
Hey @damilola-paystack, finally got around to reviewing this. I love the setup for previewing locally 🔥 I noticed that the sample responses use the schema and not actual examples. Do you know how we fix that? Also, what is the ideal flow for contributing now that we can split and bundle the file? Do I make my changes on the split files, bundle, then submit a PR? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
name: Developer Experience Improvement
about: Restructure codebase for better experience when working with the specification files
Type of change
What issue does this change solve?
This PR introduces an updated structure and tooling to improve developer experience.
Additional context
We now use Redocly to split/bundle OAS and Scalar to view spec locally.